Click any tag below to further narrow down your results
Links
Felix Rieseberg, who works on Claude, argues that most people use AI for basic tasks like speed gains when they could tackle much harder problems. He breaks ambition into four categories — speed, altitude, depth, and range — and walks through concrete techniques for each, using a quarterly business review as a running example.
- Altitude means shifting from completing individual tasks to solving the underlying outcome; instead of asking Claude to fix crashes one by one, ask it to keep your app crash-free entirely, which often requires restructuring your workflow and data access.
- Depth means pushing models to use the same tools, methods, and raw data that field experts would use, then validating results against external judges rather than asking the model to judge itself.
- Range means pulling techniques from multiple disciplines — treating a quarterly deck not as "a deck" but as "getting busy people to believe a story and decide under uncertainty," then assembling a cross-disciplinary team (analyst, journalist, short seller, forensic accountant) to bring in different perspectives.
@AnatoliKopadze on X
Andrej Karpathy walks through how he uses AI day to day, covering which model to pick, when thinking models pay off, turning one prompt into a full research report, running code through the model, and getting it to remember you across chats. The post is a pitch for a Claude-focused guide that expands on those same workflows.
- Karpathy's two-hour talk breaks down model choice, when reasoning models are worth the wait, and how to get a full research report from a single prompt.
- Two of the five segments cover letting the model run code for you and giving it persistent memory across separate chats.
- The author claims most people use about 10% of these models' capability and frames the linked guide as covering the other 90%, mapping the same ideas onto Claude features.